A club is a container with four things added: a topic, a shape, a cadence and an openness rung. A person, a kehila, a school, a bookstore, a beth din, a giyur programme or an institute may own one — and the owner kind caps how public it can ever be, because a school club full of children and a bookstore club advertising stock are not the same object.
{{ c.joinNote }}
{{ c.en }}
⚠️ {{ c.err }}
⚠️ {{ c.capNote }}
No club with that owner yet. Start one — the form is three fields and a rung.
Nothing here is approved by us. The only thing Meldar decides is the ceiling on how public it may be, and it decides that from who owns it.
{{ ownerNote }}
⚠️ {{ ownerWarn }}
{{ topicWhy }}
⚠️ {{ topicWarn }}
{{ shapeNote }}
⚠️ {{ capNote }}
{{ preview.sentence }}
One containers row with four fields added — topic, shape, cadence, openness. No new table, no second calendar, no second membership list. That is why this is a week of work and not a quarter.
A ref is not verified until it has been fetched. Verified means this project fetched it and recorded the result; proposed means the form looks right and nobody has tried it; absent means we checked and it is not in our sources — named here rather than quietly dropped, because three of the best clubs on this list are in that column.
{{ f.note }}
{{ t.why }}
{{ t.warn }}
Who knows it exists, who may read the discussion, who may join and who may post are four different questions. A single public/private switch answers them all at once and is wrong about at least two.
{{ r.line }}
⚠️ {{ r.warn }}
Not by a setting, and not by asking nicely. These caps are data — one field per owner kind — so a later hurry cannot quietly widen them.
{{ c.note }}
⚠️ {{ c.warn }}
Prompts BC1–BC12 in PROMPTS-bookclub.md · the evidence in Report 16 · the topics and caps live in meldar-bookclubs.js, so adding one is a data change. Schedules from Hebcal under CC-BY 4.0, licence position in sources/hebcal.md; text from Sefaria, version and licence named on each portion.